home *** CD-ROM | disk | FTP | other *** search
Text File | 1989-06-26 | 1.5 KB | 34 lines | [TEXT/GEOL] |
- Item 7969073 6-June-89 11:01
-
- From: BURBECK.S Burbeck, Steve
-
- To: MACAPP.TECH$ MACAPP Tech
-
- Sub: MacApp *.a to *.o issues
-
- Recently several people have run into the fact that, starting with MPW 3.0,
- buyers no longer automaticlly receive the Assembler. Since the MacApp 2.0B5
- entry in APDAlog was written before MPW 3.0 was shipped, there is no mention
- that MacApp requires the Assembler (that copy has been changed, but the revised
- copy will not show up until the next issue of APDAlog).
-
- The simplest (if expensive) solution is for everyone to buy the Assembler.
- However people in need of the assembled *.o files may also get them from a
- friend who has them. It is perfectly legal as long as both parties have
- purchased MacApp.
-
- One caution though: all but one of the *.a files (UObject.a) have conditional
- assembly directives. UTrace.a, UViewCoords.a, UMacros.a, UFailure.a, and
- UMAUtil.a all must be assembled differently for debug and nondebug. Moreover
- UCommonObjLib.a and UBusyCursor.a depend on both debug and needsROM128K, so
- there are four possible permutations of these *.o files.
-
- In 2.0B9 there will be an additional dependency: 68020|68030. With 2.0B9 we
- will ship already compiled/assembled versions of the entire library for debug
- and nondebug cases. However those who want to require 128KROM's or 68020|68030
- will still need the Assembler.
-
- Steve Burbeck
- MacApp Product Manager
-
-